Vehicle related services system and methodology

ABSTRACT

A vehicle-related services system and methodology employing at least one sensor automatically sensing at least one of the time during which a vehicle is not being operated and where the vehicle is located when it is not being operated and at least one data processor receiving information sensed by the sensor, indicating at least one of the time during which the vehicle is not being operated and where the vehicle is located when it is not being operated and providing a billing data output in respect of a vehicle-related service which is dependent on at least one of the time during which the vehicle is not being operated and where the vehicle is located when it is not being operated.

REFERENCE TO CO-PENDING APPLICATIONS

[0001] Applicants hereby claim priority of U.S. Provisional Patent Application Ser. No. 60/192,199, filed Mar. 27, 2000, entitled “Pay As You Go Fee System And Method”.

FIELD OF THE INVENTION

[0002] The present invention relates to systems and methodologies for providing, and effecting payment for, vehicle-related services in general and particularly for vehicle parking services.

BACKGROUND OF THE INVENTION

[0003] The U.S. patent literature contains a great number of patents related to systems and methodologies for providing and effecting payment for vehicle-related services.

[0004] The following U.S. patents and published PCT applications are believed to represent the state of the art with regard to systems and methodologies for providing and effecting payment for vehicle parking services:

[0005] U.S. Pat. Nos. 4,555,618; 4,876,540; 4,908,500; 4,958,064; 5,029,094; 5,034,739; 5,072,380; 5,153,559; 5,173,833; 5,266,947; 5,283,622; 5,339,000; 5,351,187; 5,414,624; 5,432,508; 5,442,348; 5,659,306; 5,710,557; 5,710,743; 5,737,710; 5,745,052; 5,748,107; 5,751,973; 5,796,084; 5,809,480; 5,819,234; 5,845,268; 5,877,704; 5,905,247; 5,910,782; 5,914,654; 5,926,546; 5,940,481; 5,980,185; 5,991,749; 6,028,550; 6,037,880; 6,061,002; 6,085,124.

[0006] WO 93/20539; WO 97/13222A1.

[0007] The following U.S. patents are believed to represent the state of the art with regard to systems and methodologies for providing and effecting payment for other types of vehicle-related services:

[0008] U.S. Pat. Nos. 4,533,962; 4,843,463; 5,210,702; 5,223,844; 5,319,374; 5,359,528; 5,422,624; 5,499,181; 5,499,182; 5,550,551; 5,583,765; 5,612,875; 5,621,166; 5,635,693; 5,642,484; 5,694,322; 5,717,374; 5,742,915; 5,797,134; 5,831,742; 5,862,500; 5,864,831; 5,914,654; 5,954,773; 5,963,129; 5,970,481; 5,974,356; 5,995,898; 6,006,148; 6,064,970; 6,067,008; 6,112,152.

SUMMARY OF THE INVENTION

[0009] The present invention seeks to provide improved, simplified and highly cost effective systems and methodologies for providing and effecting payment for vehicle-related services.

[0010] There is thus provided in accordance with a preferred embodiment of the present invention a vehicle-related services system including:

[0011] at least one sensor automatically sensing at least one of the time during which a vehicle is not being operated and where the vehicle is located when it is not being operated; and at least one data processor receiving information sensed by the at least one sensor, indicating at least one of the time during which the vehicle is not being operated and where the vehicle is located when it is not being operated and providing a billing data output in respect of a vehicle-related service which is dependent on at least one of the time during which the vehicle is not being operated and where the vehicle is located when it is not being operated.

[0012] The data processor may include a vehicle insurance billing data processor. In such a case, the billing data includes vehicle insurance billing data wherein the only variables, sensed by the on-board vehicle sensor, which are considered in the billing data are duration of vehicle operation and time of day or night of vehicle operation. The billing data may include vehicle insurance billing data wherein the billing data is not dependent on vehicle speed.

[0013] In accordance with a preferred embodiment of the present invention, the at least one sensor automatically senses the time during which a vehicle is not being operated and where the vehicle is located when it is not being operated and the at least one data processor receives information sensed by the sensor, indicating the time during which the vehicle is not being operated and where the vehicle is located when it is not being operated and provides a billing data output in respect of a vehicle-related service which is dependent on the time during which the vehicle is not being operated and where the vehicle is located when it is not being operated.

[0014] Preferably, the at least one sensor automatically senses the time during which a vehicle is parked and where the vehicle is located when it is parked and the at least one data processor receives information sensed by the at least one sensor, indicating the time during which the vehicle is parked and where the vehicle is parked and provides a parking data output in respect of parking, which is dependent on the time during which the vehicle is parked and where the vehicle is parked.

[0015] In accordance with a preferred embodiment of the present invention, the at least one sensor and the at least one data processor are operative without vehicle operator initiative to provide an indication of at least one of the time during which the vehicle is parked and where the vehicle is parked.

[0016] Preferably, the sensor is on-board the vehicle.

[0017] In accordance with a preferred embodiment of the present invention, the vehicle-related services system also includes:

[0018] at least one communicator on-board the vehicle providing an output indicating the time during which vehicle is parked and where the vehicle is parked; and

[0019] a receiver associated with the at least one data processor for receiving a communication from the at least one communicator and employing the communication for providing the information to the at least one data processor.

[0020] Preferably, the communicator communicates with the receiver at least partially not in real time.

[0021] In accordance with a preferred embodiment of the present invention, the communicator communicates with an intermediate storage and communication unit only when a vehicle in which the communicator is located is at one of a plurality of predetermined locations.

[0022] Preferably, the intermediate storage and communication unit is located at a vehicle fueling station. In accordance with a preferred embodiment of the present invention, the information includes identification of a street parking location in which the vehicle is stationary for at least a predetermined amount of time.

[0023] Preferably, the sensor is operative to sense the time during which a vehicle is not being operated without requiring interaction with an indicating device fixed in propinquity to the location.

[0024] In accordance with a preferred embodiment of the present invention, the at least one sensor is operative using triangulation to determine where a vehicle is parked.

[0025] In accordance with a preferred embodiment of the present invention, the data processor may include a vehicle insurance billing data processor. In such a case, the billing data includes vehicle insurance billing data wherein the only variables, sensed by the at least one on-board vehicle sensor, which are considered in the billing data are duration of vehicle operation and time of day or night of vehicle operation. The billing data may include vehicle insurance billing data wherein the billing data is not dependent on vehicle speed.

[0026] Preferably, the vehicle-related services system also includes an at least one on-board vehicle potential additional parking space sensor which is operative when a vehicle is stationary at a street parking place for indicating whether at least one potential additional adjacent parking place is unoccupied.

[0027] Preferably, the at least one on-board vehicle sensor provides an output indicating the existence of at least one potential unoccupied additional adjacent parking place, the system also includes

[0028] a street parking map database indicating legal street parking spaces;

[0029] a correlator receiving the output indicating existence of at least one potential unoccupied additional adjacent parking place and correlating it with the legal street parking spaces; and

[0030] an available parking communicator providing information regarding unoccupied legal street parking places to at least one driver.

[0031] There is also provided in accordance with a preferred embodiment of the present invention a vehicle-related services system including:

[0032] a plurality of on-board potential additional parking space sensors located on a plurality of vehicles, which sensors each provide an output indicating existence of at least one potential unoccupied additional adjacent parking place adjacent a vehicle located in a street parking location; and an available parking communicator employing information received from the plurality of sensors and providing information regarding unoccupied street parking places to at least one driver.

[0033] Preferably, the vehicle-related services system also includes:

[0034] a street parking map database indicating legal street parking spaces; and

[0035] a correlator receiving the output indicating existence of at least one potential unoccupied additional adjacent parking place and correlating it with the legal street parking spaces.

[0036] There is additionally provided in accordance with a preferred embodiment of the present invention a vehicle-related services system including:

[0037] at least one sensor on-board a vehicle and automatically sensing at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated;

[0038] at least one communicator on-board the vehicle providing an output indicating at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated; and

[0039] at least one data processor receiving a communication from the at least one communicator, indicating at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated and providing a billing data output in respect of a vehicle-related service which is dependent only one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated.

[0040] There is further provided in accordance with a preferred embodiment of the present invention a vehicle-related services system including:

[0041] at least one sensor on-board a vehicle and automatically sensing only at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated;

[0042] at least one communicator on-board the vehicle providing an output indicating at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated; and

[0043] at least one data processor receiving a communication from the at least one communicator, indicating at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated and providing a billing data output in respect of a vehicle-related service which is dependent on at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated.

[0044] Preferably, the sensor on-board a vehicle automatically sensing only at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated.

[0045] Preferably, the data processor includes a vehicle insurance billing data processor.

[0046] In accordance with a preferred embodiment of the present invention, the communicator communicates with an intermediate storage and communication unit only when a vehicle in which the communicator is located is at one of a plurality of predetermined locations.

[0047] Preferably, the intermediate storage and communication unit is located at a vehicle fueling station.

[0048] In accordance with a preferred embodiment of the present invention, the billing data includes vehicle insurance billing data wherein the only variables, sensed by the on-board vehicle sensor, which are considered in the billing data are duration of vehicle operation and time of day or night of vehicle operation.

[0049] Alternatively, the billing data may include vehicle insurance billing data wherein the only variables, sensed by the on-board vehicle sensor, which are considered in the billing data are duration of vehicle operation and location of the vehicle during the vehicle operation.

[0050] As a further alternatively, the billing data may include vehicle insurance billing data wherein the only variables sensed by the on-board vehicle sensor, which are considered in the billing data are duration of vehicle use and time of day or night of vehicle use.

[0051] Preferably, the vehicle-related services system includes:

[0052] at least one sensor on-board a vehicle and automatically sensing at least one of the time during which the vehicle is being operated and the distance traveled by the vehicle while it is being operated;

[0053] at least one communicator on-board the vehicle providing an output indicating at least one of the time during which the vehicle is being operated and the distance traveled by the vehicle while it is being operated; and

[0054] at least one data processor receiving a communication from the at least one communicator, indicating at least one of the time during which the vehicle is being operated and/or the distance traveled by the vehicle while it is being operated; and

[0055] providing a billing data output in respect of a vehicle-related service which is dependent only on at least one of the time during which the vehicle is being operated and the distance traveled by the vehicle while it is being operated.

[0056] Preferably, the at least one data processor includes a vehicle insurance billing data processor.

[0057] In accordance with a preferred embodiment of the present invention, the billing data includes vehicle insurance billing data wherein the only variables, sensed by the on-board vehicle sensor, which are considered in the billing data are time of day and date of vehicle operation and distance covered during the vehicle operation.

[0058] Preferably, the communicator communicates with an intermediate storage and communication unit only when a vehicle in which the communicator is located is at one of a plurality of predetermined locations.

[0059] In accordance with a preferred embodiment of the present invention, the intermediate storage and communication unit is located at a vehicle fueling station.

[0060] Preferably, the billing data includes vehicle insurance billing data wherein the billing data is not dependent on vehicle speed.

[0061] In accordance with a preferred embodiment of the present invention, the at least one data processor includes a vehicle parking billing data processor.

[0062] Preferably, the at least one sensor and the at least one data processor are operative without vehicle operator initiative to provide an indication at least one of the time during which the vehicle is parked and where the vehicle is parked.

[0063] In accordance with a preferred embodiment of the present invention, the at least one sensor is operative to sense the time during which a vehicle is being operated without requiring interaction with an indicating device fixed in propinquity to the location.

[0064] Preferably, the communicator communicates with the at least one data processor at least partially not in real time.

[0065] There is also provided in accordance with a preferred embodiment of the present invention a vehicle-related fee payment system including:

[0066] at least one sensor on-board a vehicle and automatically sensing at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated;

[0067] at least one communicator on-board the vehicle providing an output indicating at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated; and

[0068] at least one data processor receiving a communication from the at least one communicator, indicating at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated and providing a billing data output in respect of a vehicle-related use fee which is dependent on the time during which the vehicle is being operated.

[0069] Preferably, the communicator communicates with the at least one data processor at least partially not in real time.

[0070] In accordance with a preferred embodiment of the present invention, the communicator communicates with an intermediate storage and communication unit only when a vehicle in which the communicator is located is at one of a plurality of predetermined locations, such as a vehicle fueling station.

[0071] In accordance with a preferred embodiment of the present invention, the data processor provides a billing data output in respect of a vehicle-related use fee which is dependent on the duration of vehicle operation and time of day of vehicle operation.

[0072] Preferably, the at least one data processor provides a billing data output in respect of a vehicle-related use fee which is also dependent on where the vehicle is located during vehicle operation.

[0073] In accordance with a preferred embodiment of the present invention, the billing data output is dependent on the time during which the vehicle is being operated and on a level of pollution being created by the vehicle.

[0074] There is additionally provided in accordance with a preferred embodiment of the present invention a vehicle-related fee payment system including:

[0075] at least one sensor for automatically sensing the passage of a vehicle along a given road;

[0076] at least one data processor receiving a communication from the at least one sensor, indicating the passage of the vehicle along a given road at a given time and providing a billing data output in respect of a vehicle-related use fee which is dependent only on the time during which the vehicle is passing along the given road.

[0077] There is further provided in accordance with a preferred embodiment of the present invention a vehicle-related fee payment system including:

[0078] at least one sensor on-board a vehicle and automatically sensing at least one of the time during which the vehicle is being operated;

[0079] at least one communicator on-board the vehicle providing an output indicating at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated; and

[0080] at least one data processor receiving a communication from the at least one communicator, indicating at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated and providing a billing data output in respect of a vehicle-related use fee which is dependent on the region in which a vehicle is operating and the time of day during which the vehicle is being operated in the region.

[0081] There is additionally provided a vehicle-related services method including:

[0082] automatically sensing the time during which a vehicle is not being operated and where the vehicle is located when it is not being operated and receiving information indicating the time during which the vehicle is not being operated and where the vehicle is located when it is not being operated and providing a parking data output in respect of a vehicle-related service which is dependent on the time during which the vehicle is not being operated and where the vehicle is located when it is not being operated.

[0083] Preferably, the method also includes providing an indication of the time during which the vehicle is parked and where the vehicle is parked substantially without operator intervention.

[0084] The above method preferably also includes communicating an indication of the time during which the vehicle is parked and where the vehicle is parked to a receiver at least partially not in real time.

[0085] Preferably, the automatic sensing takes place without requiring interaction with an indicating device fixed in propinquity to a parking location.

[0086] There is additionally provided in accordance with a preferred embodiment of the present invention a vehicle-related services method including:

[0087] providing outputs indicating existence of at least one potential unoccupied additional adjacent parking place adjacent a plurality of vehicles located in street parking locations and employing the outputs received from the plurality of vehicles and providing information regarding unoccupied street parking places to at least one driver.

[0088] Further in accordance with a preferred embodiment of the present invention there is provided a vehicle-related services method including:

[0089] automatically sensing at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated;

[0090] communicating an output indicating at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated; and

[0091] receiving a communication indicating at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated and providing an insurance billing data output in respect of vehicle insurance which is dependent only on at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated.

[0092] Preferably, communicating takes place only when a vehicle is at one of a plurality of predetermined locations.

[0093] In accordance with a preferred embodiment of the present invention, the billing data includes vehicle insurance billing data wherein the only automatically sensed variables which are considered in the billing data are duration of vehicle operation and time of day or night of vehicle operation.

[0094] There is additionally provided in accordance with a preferred embodiment of the present invention a vehicle-related fee payment method including:

[0095] automatically sensing at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated;

[0096] providing an output indicating at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated; and

[0097] receiving the output indicating at least one of the time during which the vehicle is being operated and where the vehicle is located when it is being operated and providing a billing data output in respect of a vehicle-related use fee which is dependent on the time during which the vehicle is being operated.

[0098] Preferably, the billing data output in respect of a vehicle-related use fee is dependent on the duration of vehicle operation and time of day of vehicle operation.

[0099] In accordance with a preferred embodiment of the present invention the billing data output is dependent on the time during which the vehicle is being operated and on a level of pollution being created by the vehicle.

[0100] There is additionally provided in accordance with a preferred embodiment of the present invention a vehicle-related services method including:

[0101] automatically sensing the time during which the vehicle is being operated and the distance traveled by the vehicle while it is being operated;

[0102] communicating an output indicating the time during which the vehicle is being operated and the distance traveled by the vehicle while it is being operated; and

[0103] receiving a communication indicating the time during which the vehicle is being operated and the distance traveled by the vehicle while it is being operated and providing an insurance billing data output in respect of vehicle insurance which is dependent only on the time during which the vehicle is being operated and the distance traveled by the vehicle while it is being operated.

[0104] Preferably, the billing data includes vehicle insurance billing data wherein the only automatically sensed variables which are considered in the billing data are the distance traveled by the vehicle while it is being operated and time of day or night of vehicle operation.

[0105] Preferably in all embodiments of the invention, the sensor automatically senses the time of day and date when the vehicle is not being operated.

[0106] Additionally or alternatively in all embodiments of the invention, the sensor automatically senses the time duration during which the vehicle is not being operated.

[0107] It is appreciated that the various embodiments described hereinabove may be employed individually or alternatively any suitable combination of such embodiments may be employed.

BRIEF DESCRIPTION OF THE DRAWINGS

[0108] The present invention will be understood and appreciated more fully from the following detailed description, taken in conjunction with the drawings in which:

[0109]FIGS. 1A, 1B and 1C are simplified pictorial illustrations of three alternative embodiments of parking payment systems and methodologies constructed and operative in accordance with a preferred embodiment of the present invention;

[0110]FIG. 2 is a simplified pictorial illustration of a preferred embodiment of a parking location and payment system and methodology constructed and operative in accordance with a preferred embodiment of the present invention;

[0111]FIGS. 3A, 3B and 3C are simplified block diagram illustrations of three alternative embodiments of parking payment systems and methodologies constructed and operative in accordance with a preferred embodiment of the present invention and corresponding to FIGS. 1A, 1B and 1C, respectively;

[0112]FIGS. 4A, 4B and 4C are simplified flow charts illustrating the operation of the three alternative embodiments of parking payment systems and methodologies of FIGS. 1A & 3A, 1B & 3B and 1C & 3C respectively;

[0113]FIG. 5 is a simplified block diagram illustration of an embodiment of a parking location and payment system and methodology constructed and operative in accordance with a preferred embodiment of the present invention and corresponding to FIG. 2;

[0114]FIG. 6 is a simplified flow chart illustrating an embodiment of the parking location and payment system and methodology of FIGS. 2 & 5;

[0115]FIGS. 7A, 7B and 7C are simplified pictorial illustrations of three alternative embodiments of vehicle-related services payment systems and methodologies constructed and operative in accordance with a preferred embodiment of the present invention;

[0116]FIGS. 8A, 8B and 8C are simplified block diagram illustrations of three alternative embodiments of payment systems and methodologies constructed and operative in accordance with a preferred embodiment of the present invention and corresponding to FIGS. 7A, 7B & 7C respectively;

[0117]FIGS. 9A, 9B and 9C are simplified flow charts illustrating the operation of the three alternative embodiments of payment systems and methodologies of FIGS. 7A & 8A, 7B & 8B and 7C & 8C respectively;

[0118]FIGS. 10A, 10B and 10C are simplified pictorial illustrations of preferred embodiments of vehicle fee payment systems and methodologies constructed and operative in accordance with three alternative preferred embodiments of the present invention;

[0119]FIGS. 11A, 11B and 11C are simplified block diagram illustrations of preferred embodiments of vehicle fee payment systems and methodologies constructed and operative in accordance with a preferred embodiment of the present invention and corresponding to FIGS. 10A, 10B and 10C respectively;

[0120]FIGS. 12A, 12B and 12C are simplified flow charts illustrating the operation of preferred embodiments of vehicle fee payment systems and methodologies of FIGS. 10A & 11A, 10B & 11B and 10C & 11C respectively;

[0121]FIGS. 13A, 13B and 13C are simplified pictorial illustrations of three alternative embodiments of vehicle-related services payment systems and methodologies constructed and operative in accordance with another preferred embodiment of the present invention;

[0122]FIGS. 14A, 14B and 14C are simplified block diagram illustrations of three alternative embodiments of payment systems and methodologies constructed and operative in accordance with another preferred embodiment of the present invention and corresponding to FIGS. 13A, 13B & 13C respectively; and

[0123]FIGS. 15A, 15B and 15C are simplified flow charts illustrating the operation of the three alternative embodiments of payment systems and methodologies of FIGS. 13A & 14A, 13B & 14B and 13C & 14C respectively.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

[0124] Reference is now made to FIGS. 1A, 1B and 1C, which are simplified pictorial illustrations of three alternative embodiments of parking payment systems and methodologies constructed and operative in accordance with a preferred embodiment of the present invention.

[0125]FIG. 1A illustrates a GPS-based system for effecting payment for parking without requiring any driver intervention. As shown in FIG. 1A, a vehicle 100 equipped with a GPS receiver 102 or similar location determining device is parked by a driver. Without requiring any intervention by the driver, a parking communicator 104, receiving a location input from GPS receiver 102, transmits a message in a wireless manner to a central unit 106, which in turn provides data used for effecting payment for parking.

[0126] The message typically includes data relating to the identity of the vehicle parked, the parking location, the date and the start time of parking.

[0127] In the illustrated embodiment, when the driver removes the vehicle 100 from the parking location, the parking communicator 104 transmits a further message in a wireless manner to central unit 106. This message typically includes data relating to the identity of the vehicle parked, the parking location, the date, the start time of parking and the finish time of parking, i.e. the time that the vehicle 100 exits the parking location.

[0128] As illustrated in FIG. 1A, additionally or alternatively to transmittal of a message when the vehicle enters and/or exits the parking location, a composite message may be transmitted at any time from the vehicle 100 to the central unit 106. Such a composite message may include messages relating to a plurality of parking events. In respect of each parking event, the message typically includes data relating to the identity of the vehicle parked, the parking location, the date, the start time of parking and the finish time of parking.

[0129] Composite messages may be transmitted, for example, at predetermined times or upon accumulation of data relating to a predetermined number of parking events or based on any other suitable criterion or combination of criteria.

[0130] It is appreciated that no message need be sent at the time of parking or at the termination of parking. It is also appreciated that when a message is sent at the time of parking, the message sent at the termination of parking need not include data relating to the start time of parking.

[0131] In the embodiment of FIG. 1A, wireless communication is preferably effected via a cellular communication system, but may alternatively be effected by any other suitable wireless communication facility.

[0132]FIG. 1B also illustrates a GPS-based system for effecting payment for parking without requiring any driver intervention. As shown in FIG. 1B, a vehicle 200 equipped with a GPS receiver 202 or similar location determining device is parked by a driver. Without requiring any intervention by the driver, a parking recorder 204, receiving a location input from GPS receiver 202, records data relating to the parking location, the date and the start time of parking.

[0133] In the illustrated embodiment, when the driver removes the vehicle 200 from the parking location, the parking recorder 204 records data relating to the parking location, the date, the finish time of parking.

[0134] As illustrated in FIG. 1B, when the vehicle 200 is located at one of a multiplicity of predetermined download locations, such as a suitably equipped filling station, for example, a gasoline station or an electric vehicle recharging station, the parking recorder 204 downloads data relating to a plurality of parking events over a time period extending from the preceding download, via a suitable communicator 206, typically in a wireless manner, to an intermediate storage and communication unit 208, typically located at the filling station. The intermediate storage and communication unit 208 preferably receives and stores data relating to a plurality of parking events in respect of a multiplicity of vehicles and communicates this data, in a composite message, preferably in a wireless manner, to a central unit 210. Alternatively or additionally, download locations may be found at other places, such as road intersections, parking lots and malls.

[0135] Typically, the composite message may be transmitted at any time from the intermediate storage and communication unit 208 to the central unit 210. Such a composite message typically includes messages relating to a plurality of parking events for a multiplicity of different vehicles. In respect of each parking event, the message typically includes data relating to the identity of the vehicle parked, the parking location, the date, the start time of parking and the finish time of parking.

[0136] Composite messages may be transmitted at predetermined times or upon accumulation of data relating to a predetermined number of parking events or based on any other suitable criterion or combination of criteria.

[0137]FIG. 1C illustrates a further alternative embodiment of a system for effecting payment for parking without requiring any driver intervention. As shown in FIG. 1C, a vehicle 300, equipped with a transmitter 302, which transmits a wireless coded signal identifying the vehicle, is parked. Without requiring any intervention by the driver, the coded signal transmitted by transmitter 302 is received by at least two and preferably three angular sensitive receivers 304, which are located in general propinquity to the parking location of the vehicle 300 and communicate with a central unit 306.

[0138] Typically, the receipt of outputs from the receivers 304 enables the location of the vehicle 300 to be determined using conventional triangulation technology. The timing of receipt of the coded signals as well as sensed change or lack of change in the vehicle location provides an indication of the parking start time and parking finish time, which, when received by the central unit 306, together with vehicle identification data, enable payment for parking to be effected.

[0139] Preferably communication between the various receivers 304 and the central unit 306 takes place intermittently rather than continuously, for enhanced economy. Such communication preferably includes composite messages including messages relating to a plurality of parking events for a multiplicity of different vehicles. In respect of each parking event, the message typically includes data relating to the identity of the vehicle parked, parking location triangulation information, the date, the start time of parking and the finish time of parking.

[0140] Reference is now made to FIG. 2, which is a simplified pictorial illustration of a preferred embodiment of a parking location and payment system and methodology constructed and operative in accordance with a preferred embodiment of the present invention.

[0141]FIG. 2 illustrates a GPS-based system for finding available parking locations and for effecting payment for parking without requiring any driver intervention. Similarly to the system shown in FIG. 1A, a vehicle 400, equipped with a GPS receiver 402 or similar location determining device, is parked by a driver. Without requiring any intervention by the driver, a parking communicator 404, receiving a location input from GPS receiver 402, transmits a message in a wireless manner to a central unit 406, which in turn provides data used for effecting payment for parking.

[0142] The message typically includes data relating to the identity of the vehicle parked, the parking location, the date and the start time of parking. As described hereinabove with reference to FIG. 1A, messages are sent thereafter indicating parking finish time in one of a number of alternative manners.

[0143] In the embodiment of FIG. 2, in addition to the functionality described hereinabove with reference to FIG. 1A, the vehicle is preferably provided with at least one sensor 408 indicating existence of at least one potential unoccupied additional adjacent parking place. The sensor 408 is typically a laser, radar or ultrasonic range finder and is typically mounted so as to be either front facing or rearward facing so as to identify the existence of an empty parking space. The output of sensor 408 is communicated while the vehicle is parked, preferably in a wireless manner, to a parking location center 410, which may integrated with the central unit 406 or may employ all or part of the same computer hardware.

[0144] The parking location center 410 typically maintains a street parking map database indicating legal street parking spaces and includes functionality providing a correlator. The correlator receives an output from sensor 408 indicating the existence of at least one potential unoccupied additional adjacent parking place and correlates it with legal street parking spaces, using the database. An available parking communicator 412, associated with the parking location center 410, provides information regarding unoccupied legal street parking places to at least one driver, preferably in a wireless manner. Preferably communicator 412 broadcasts data indicating the availability of parking spaces at given locations either by direct wireless communication, wireless broadcast or via the Internet.

[0145] In the embodiment of FIG. 2, wireless communication from sensors 408 to parking location center 410 is preferably effected via communicator 404 and a cellular communication system, but may alternatively be effected by any other suitable wireless communication facility. Wireless communication from parking communicator 404 to central unit 406 may also be effected via a cellular communication facility. The communication from sensors 408 is preferably immediate upon a change of status from a status of availability to a status of unavailability and vice versa, while the communication from parking communicator 404 is normally intermittent, for reasons of economy.

[0146] It is appreciated that although the vehicle location functionality of FIG. 2 is shown in combination with a parking payment system, it is also possible that the vehicle location functionality be provided in a stand-alone form, such as without a parking payment system or with a parking payment system other than that of the type described hereinabove with reference to FIG. 1A. For example the vehicle location functionality of FIG. 2 may be provided in association with a parking payment system of the type described hereinabove with reference to either of FIGS. 1B and 1C.

[0147] Reference is now made to FIGS. 3A, 3B and 3C, which are simplified block diagram illustrations of three alternative embodiments of parking payment systems and methodologies constructed and operative in accordance with a preferred embodiment of the present invention and corresponding to FIGS. 1A, 1B and 1C respectively.

[0148]FIG. 3A illustrates, in block diagram form, the GPS-based system for effecting payment for parking shown in FIG. 1A. Vehicle 100 is equipped with GPS receiver 102, which receives inputs from GPS satellites 500. GPS receiver 102 outputs vehicle location data to a CPU 502, which preferably but not necessarily interfaces with a memory 504 and a display 506. Parking communicator 104 receives the location input from GPS receiver 102 via CPU 502 and transmits a message in a wireless manner to central unit 106, which in turn provides data used for effecting payment for parking to a billing system 508. It is appreciated that the billing system may employ various criteria in addition to the data received from central unit 106.

[0149] The central unit 106 typically includes a wireless receiver or transceiver 510, which interfaces with a CPU 512. CPU 512 preferably interfaces with a database 514. The CPU 512 and the database 514 preferably cooperate for processing the data received from the vehicle 100 into a form useful by the billing system 508.

[0150]FIG. 3B illustrates, in block diagram form, the GPS-based system for effecting payment for parking shown in FIG. 1B. Vehicle 200 is equipped with GPS receiver 202, which receives inputs from GPS satellites 600. GPS receiver 202 outputs vehicle location data to parking recorder 204, which typically includes a CPU 602 which interfaces with a memory 604 and optionally with a display 606. Communicator 206 receives all relevant parking information, stored in memory 604, for each parking event via CPU 602 and transmits a message including this information in a wireless manner to intermediate storage and communication unit 208, typically including a wireless receiver or transceiver 608, which outputs to a memory 610 via a CPU 611.

[0151] Intermediate storage and communication unit 208 also includes a communicator 612 which typically transmits a composite message in respect of multiple parking events of multiple vehicles to central unit 210.

[0152] Additionally, a facility optionally may be provided for enabling direct communication between vehicle mounted communicator 206 and central unit 210.

[0153] The central unit 210 typically includes a wireless receiver or transceiver 613, which interfaces with a CPU 614. Alternatively, communication between communicator 612 and receiver 613 may be wired rather than wireless. CPU 614 preferably interfaces with a database 616. The CPU 614 and the database 616 preferably cooperate for processing the data received from a multiplicity of vehicles 200 into a form useful by a billing system 618.

[0154]FIG. 3C illustrates, in block diagram form, the triangulation-based system for effecting payment for parking shown in FIG. 1C. Vehicle 300 includes transmitter 302, which transmits a wireless coded signal identifying the vehicle, without requiring any intervention by the driver.

[0155] The coded signal transmitted by transmitter 302 is received by at least two and preferably three receivers 304 which are located in general propinquity to the parking location of the vehicle 300 and communicate with a central unit 306.

[0156] Each receiver 304 preferably includes a directional receiver 700 which interfaces with a CPU 702. CPU 702 interfaces with a memory 704 and with a communicator 706.

[0157] Central unit 306 typically includes a communicator 708 which interfaces with a CPU 710. CPU preferably interfaces with a database 712 and outputs to a billing system 714. Communication between communicators 706 and 708 may be wired or wireless.

[0158] Each receiver 304 intermittently provides outputs indicating the start time and the finish time for each parking event of each identified vehicle, as well as the angular direction from which it was received.

[0159] As noted above with reference to FIG. 1C, using conventional triangulation technology, the receipt of the outputs of the receivers 304 enables the location of the vehicle 300 to be determined by central unit 306. The timing of receipt of the coded signals by receivers 304 as well as sensed change or lack of change in the vehicle location provides an indication of the parking start time and parking finish time, which, when received by the central unit 306 together with vehicle identification data, enable payment for parking to be effected.

[0160] Reference is now made to FIGS. 4A, 4B and 4C, which are simplified flow charts illustrating the operation of the three alternative embodiments of parking payment systems and methodologies of FIGS. 3A, 3B and 3C respectively.

[0161] Referring now to FIG. 4A, it is seen that an initial determination is made retroactively as to whether a vehicle has parked. This determination is typically made by sensing whether a vehicle has been motionless for at least a predetermined time, such as, for example five minutes. If a vehicle is determined to have been parked, the start time of parking is determined. The start time normally is earlier than the time that the determination was made. The system may or may not send a start parking message to central unit 106 at this stage.

[0162] The start time of parking is typically stored in memory 504 (FIG. 3A).

[0163] A determination is made of when the vehicle first moves from its parking location. Once such movement is sensed, the exit time of parking is determined. The exit time may be communicated to the central unit 106 upon exit. If the start time has not yet been communicated to the central unit 106, both the start time and exit time may be communicated together. As a further alternative, the start and exit time of each parking event may be stored in memory 504 for later transmittal to the central unit 106.

[0164] Referring now to FIG. 4B, which describes the system of FIGS. 1B and 3B, it is seen that an initial determination is also made retroactively as to whether a vehicle has parked. This determination is typically made by sensing whether a vehicle has been motionless for at least a predetermined time, such as, for example five minutes. If a vehicle is determined to have been parked, the start time of parking is determined. The start time normally is earlier than the time that the determination was made.

[0165] The start time of parking is typically stored in memory 604 (FIG. 3B).

[0166] A determination is made of when the vehicle first moves from its parking location. Once such movement is sensed, the exit time of parking is determined. The start and exit time of each parking event are stored in memory 604 for later transmittal to the intermediate storage and communication unit 208.

[0167] When the vehicle reaches a download location, such as a filling station, the contents of memory 604 are preferably downloaded in a composite message to intermediate storage and communication unit 208.

[0168] Communicator 612 of intermediate storage and communication unit 208 typically transmits a composite message in respect of multiple parking events of multiple vehicles to central unit 210.

[0169] Optionally direct communication between vehicle mounted communicator 206 and central unit 210 may be provided.

[0170] Referring now to FIG. 4C, which describes the operation of the embodiment of FIGS. 1C and 3C, it is seen that an initial determination is made by each receiver 304 retroactively as to whether a vehicle has parked. This determination is typically made by sensing whether a vehicle has been motionless for at least a predetermined time, such as, for example five minutes. If a vehicle is determined to have been parked, the start time of parking is determined. The start time normally is earlier than the time that the determination was made.

[0171] The start time of parking is typically stored in memory 704 (FIG. 3C) of each receiver.

[0172] A determination is made by each receiver of when the vehicle first moves from its parking location. Once such movement is sensed, the exit time of parking is determined. The start and exit time of each parking event are stored in memory 704.

[0173] Intermittently the start and exit times of a plurality of vehicles are transmitted to central unit 306 by receivers 304. The central unit, by employing triangulation techniques, determines the location of each vehicle and associates it with the corresponding start and exit times for each parking event.

[0174] Reference is now made to FIG. 5, which is a simplified block diagram illustration of an embodiment of a parking location and payment system and methodology constructed and operative in accordance with a preferred embodiment of the present invention and corresponding to FIG. 2.

[0175]FIG. 5 illustrates, in block diagram form, the GPS-based system for finding available parking locations and for effecting payment for parking without requiring any driver intervention shown in FIG. 2.

[0176] Vehicle 400 is equipped with GPS receiver 402, which receives inputs from GPS satellites 800. GPS receiver 402 outputs vehicle location data to a CPU 802, which preferably but not necessarily interfaces with a memory 804 and a display 806. Parking communicator 404 receives the location input from GPS receiver 402 via CPU 802 and transmits a message in a wireless manner to central unit 406, which in turn provides data used for effecting payment for parking to a billing system 808.

[0177] In the embodiment of FIGS. 2 and 5, in addition to the functionality described hereinabove, the vehicle is preferably provided with at least one sensor 408 indicating existence of at least one potential unoccupied additional adjacent parking place. As noted hereinabove with reference to FIG. 2, the sensor 408 is typically a laser range finder, a radar device or an ultrasonic range finder and is typically mounted so as to be either front facing or rearward facing so as to identify the existence of an empty parking space.

[0178] The output of sensor 408 is communicated while the vehicle is parked, preferably in a wireless manner, preferably via communicator 404 to parking location center 410, which may be identical to central unit 406 or may employ all or part of the same computer hardware.

[0179] The central unit 406 typically includes a wireless receiver or transceiver 810, which interfaces with a CPU 812. CPU 812 preferably interfaces with a database 814. The CPU 812 and the database 814 preferably cooperate for processing the data received from the vehicle 400 into a form useful by the billing system 808.

[0180] As noted hereinabove with reference to FIG. 2, parking location center 410 typically maintains a street parking map database indicating legal street parking spaces and includes functionality providing a correlator. The correlator, here embodied in a CPU 816 receives an output from sensor 408 via communicator 817, indicating the existence of at least one potential unoccupied additional adjacent parking place and correlates it with legal street parking spaces, using a central database 818.

[0181] An available parking communicator 412, associated with the parking location center 410, provides information regarding unoccupied legal street parking places to at least one driver, preferably in a wireless manner. Preferably communicator 412 broadcasts data indicating the availability of parking spaces at given locations either by direct wireless communication, wireless broadcast or via the Internet.

[0182] It is appreciated that although the vehicle location functionality of FIGS. 2 & 5 is shown in combination with a parking payment system, it is also possible that the vehicle location functionality be provided in a stand-alone form, such as without a parking payment system or with a parking payment system other than that of the type described hereinabove with reference to FIGS. 1A, 3A & 4A. For example, the vehicle location functionality of FIGS. 2 & 5 may be provided in association with a parking payment system of the type described hereinabove with reference to either of FIGS. 1B and 1C.

[0183] Reference is now made to FIG. 6, which is a simplified flow chart illustrating an embodiment of the parking location and payment system and methodology of FIGS. 2 & 5. As seen in FIG. 6, the embodiment of FIGS. 2 & 5 provides parking payment functionality, which may be identical to that of FIG. 4A. In addition to the parking payment functionality, the embodiment of FIGS. 2 & 5 provides parking location functionality as described hereinbelow:

[0184] A determination is made whether vehicle 400 has parked. If so, a determination is made, using sensor 408, whether an adjacent parking space is empty. If so, a message is transmitted forthwith to parking location center 410. The parking space center 410, makes a determination as to whether the sensed empty parking space is a legal parking space. If so, it notifies other drivers by any suitable technique.

[0185] Thereafter, if the vehicle remains parked and the sensed empty parking space remains empty, no further message is transmitted to parking location center 410. If, however, the previously empty parking space is subsequently filled, a suitable message is sent to parking location center 410, preferably causing an appropriate notification to be broadcast thereby to other vehicles.

[0186] Reference is now made to FIGS. 7A, 7B and 7C, which are simplified pictorial illustrations of three alternative embodiments of vehicle-related services payment systems and methodologies constructed and operative in accordance with a preferred embodiment of the present invention and which preferably are characterized in that the payment in respect of a vehicle-related service is dependent on at least one of whether and when the vehicle is being operated.

[0187] Important examples of such systems and methodologies include vehicle insurance billing and vehicle fee payment systems wherein the only variables sensed by an on-board vehicle sensor, which are considered in the billing data are duration of vehicle use and time of day or night of vehicle use. Other types of such systems and methodologies are also within the scope of the present invention.

[0188] Turning now to FIG. 7A, there is seen a vehicle 900 equipped with a vehicle movement or other vehicle operation determining sensor 902. Sensor 902 is typically a vibration sensor, an electrical or acoustic motor operation sensor or a driver presence sensor. Sensor 902 need not necessarily be connected to the electrical system of the vehicle 900.

[0189] Without requiring any intervention by the driver, the times when a driver moves the vehicle 900 and subsequently parks the vehicle 900 are recorded in a memory 904, which may store a series of vehicle operation start and stop records.

[0190] As illustrated in FIG. 7A, when the vehicle 900 is located at one of a multiplicity of predetermined download locations, such as a suitably equipped filling station, an on-board communicator 906 downloads data stored in memory 904 and relating to a plurality of vehicle operation start and stop events, typically in a wireless manner, to an intermediate storage and communication unit 908, typically located at the filling station. The intermediate storage and communication unit 908 preferably receives and stores data relating to a plurality of vehicle operation start and stop events in respect of a multiplicity of vehicles and communicates this data, in a composite message, preferably in a wireless manner, to a central unit 910. Alternatively or additionally, download locations may be found at other locations, such as road intersections, parking lots and malls.

[0191] Typically, the composite message may be transmitted at any time from the intermediate storage and communication unit 908 to the central unit 910. Such a composite message typically includes messages relating to a plurality of vehicle operation start and stop events for a multiplicity of different vehicles. In respect of each such event, the message typically includes data relating to the identity of the vehicle, the date, the start time of vehicle operation and the stop time of vehicle operation.

[0192] Composite messages may be transmitted at predetermined times or upon accumulation of data relating to a predetermined number of events or based on any other suitable criterion or combination of criteria.

[0193] Turning now to FIG. 7B, there is seen a vehicle 1000 equipped with a movement or operation determining sensor 1002. Sensor 1002 is typically a vibration sensor, an electrical or acoustic motor operation sensor or a driver presence sensor. Sensor 1002 need not necessarily be connected to the electrical system of the vehicle 1000.

[0194] Without requiring any intervention by the driver, the times when a driver moves the vehicle 1000 and subsequently parks the vehicle 1000 are recorded in a memory 1004, which may store a series of vehicle operation start and stop records.

[0195] As illustrated in FIG. 7B, an on-board communicator 1006 downloads data stored in memory 1004 and relating to a plurality of vehicle operation start and stop events, in a composite message, preferably in a wireless manner to a central unit 1010.

[0196] Typically, the composite message may be transmitted at any time from the communicator 1006 to the central unit 1010. Such a composite message typically includes messages relating to a plurality of vehicle operation start and stop events. In respect of each such event, the message typically includes data relating to the identity of the vehicle, the date, the start time of vehicle operation and the stop time of vehicle operation.

[0197] Composite messages may be transmitted at predetermined times or upon accumulation of data relating to a predetermined number of events or based on any other suitable criterion or combination of criteria.

[0198] Turning now to FIG. 7C, there is seen a vehicle 1100 equipped with a GPS receiver 1102 receiving inputs from satellites 1103 or a similar location determining devices. The GPS receiver 1102 senses when the location of the vehicle changes.

[0199] Without requiring any intervention by the driver, the times when a driver moves the vehicle 1100 and subsequently parks the vehicle 1100 are recorded in a memory 1104, which may store a series of vehicle operation start and stop records.

[0200] As illustrated in FIG. 7C, an on-board communicator 1106 downloads data stored in memory 1104 and relating to a plurality of vehicle operation start and stop events, in a composite message, preferably in a wireless manner to a central unit 1110.

[0201] Typically, the composite message may be transmitted at any time from the communicator 1106 to the central unit 110. Such a composite message typically includes messages relating to a plurality of vehicle operation start and stop events. In respect of each such event, the message typically includes data relating to the identity of the vehicle, the date, the start time of vehicle operation and the stop time of vehicle operation.

[0202] Composite messages may be transmitted at predetermined times or upon accumulation of data relating to a predetermined number of events or based on any other suitable criterion or combination of criteria.

[0203] Additionally or alternatively, communicator 1106 may communicate with the central unit 1110 via an intermediate storage and communication unit 1108, much in the same way as described hereinabove with reference to FIG. 7A.

[0204] Reference is now made to FIGS. 8A, 8B and 8C, which are simplified block diagram illustrations of three alternative embodiments of vehicle-related services payment systems and methodologies constructed and operative in accordance with a preferred embodiment of the present invention and corresponding to FIGS. 7A, 7B & 7C respectively.

[0205] Turning now to FIG. 8A, it is seen that vehicle 900 includes a CPU 1202, which interfaces with movement or operation determining sensor 902, memory 904 and on-board communicator 906.

[0206] As illustrated in FIG. 8A, when the vehicle 900 is located at one of a multiplicity of predetermined download locations, such as a suitably equipped filling station, on-board communicator 906 downloads data stored in memory 904 relating to a plurality of vehicle operation start and stop events, typically in a wireless manner, to intermediate storage and communication unit 908. The intermediate storage and communication unit 908 includes a receiver or transceiver 1204 which interfaces with a CPU 1206. The CPU 1206 interfaces with a memory 1208 which stores data relating to a plurality of vehicle operation start and stop events in respect of a multiplicity of vehicles and with a communicator 1210, which communicates this data, in a composite message, preferably in a wireless manner to central unit 910.

[0207] Central unit 910 preferably includes a receiver or transceiver 1212 which interfaces with a CPU 1214. The CPU 1214 in turn interfaces with a database 1216. The database 1216 accumulates the content of the composite messages received by the central unit 910 and supplies this content in an appropriate form to a billing system 1218. The billing system 1218 may take into account appropriate additional criteria, such as, for example in the case of insurance, the age and driving experience of a driver and various characteristics of the vehicle or in the case of vehicle-related fees, the type and weight of the vehicle.

[0208] Turning now to FIG. 8B, it is seen that vehicle 1000 includes a CPU 1302, which interfaces with movement or operation determining sensor 1002, memory 1004 and on-board communicator 1006.

[0209] As illustrated in FIG. 8B, on-board communicator 1006 downloads data stored in memory 1004 and relating to one or more vehicle operation start and stop events, typically in a wireless manner, to central unit 1010. Central unit 1010 preferably includes a receiver or transceiver 1312 which interfaces with a CPU 1314. The CPU 1314 in turn interfaces with a database 1316. The database 1316 accumulates the content of the composite messages received by the central unit 1010 and supplies this content in an appropriate form to a billing system 1318.

[0210] Turning now to FIG. 5C, it is seen that vehicle 1100 includes a GPS receiver 1102 receiving inputs from satellites 1103. GPS receiver 1102 outputs to a CPU 1402 which interfaces with memory 1104 and with an optional display 1404. CPU also interfaces with on-board communicator 1106.

[0211] As illustrated in FIG. 8C, when the vehicle 1100 is located at one of a multiplicity of predetermined download locations, such as a suitably equipped filling station, on-board communicator 1106 downloads data stored in memory 1104 and relating to a plurality of vehicle operation start and stop events, typically in a wireless manner, to intermediate storage and communication unit 1108. The intermediate storage and communication unit 1108 includes a receiver or transceiver 1404 which interfaces with a CPU 1406. The CPU 1406 interfaces with a memory 1408 which stores data relating to a plurality of vehicle operation start and stop events in respect of a multiplicity of vehicles and with a communicator 1410, which communicates this data, in a composite message, preferably in a wireless manner to central unit 1110.

[0212] Central unit 1110 preferably includes a receiver or transceiver 1412 which interfaces with a CPU 1414. The CPU 1414 in turn interfaces with a database 1416. The database accumulates the content of the composite messages received by the central unit 1110 and supplies this content in an appropriate form to a billing system 1418.

[0213] Additionally or alternatively, communicator 1106 may communicate directly with the central unit 1110, bypassing the intermediate storage and communication unit 1108. In such a case, units 1108 may be obviated.

[0214] Reference is now made to FIGS. 9A, 9B and 9C, which are simplified flow charts illustrating the operation of the three alternative embodiments of payment systems and methodologies of FIGS. 7A & 8A, 7B & 8B and 7C & 8C, respectively.

[0215] Turning now to FIG. 9A, it is seen that a determination of whether vehicle 900 is being operated is made repeatedly. If the vehicle is being operated, a determination of the start time of vehicle operation is made and the start time is stored in memory 904.

[0216] While the vehicle is operating, a determination of whether vehicle 900 is still being operated is made repeatedly. If the vehicle ceases operation for at least a predetermined time, typically 5 minutes, a determination of the stop time of vehicle operation is made and the stop time is stored in memory 904,

[0217] At any suitable time when the vehicle is located at a suitable download location, whether the vehicle is operating or not operating, the contents of the memory 904 may be downloaded to the intermediate storage and communication unit 908 and thence to the central unit 910.

[0218] Turning now to FIG. 9B, it is seen that a determination of whether vehicle 1000 is being operated is made repeatedly. If the vehicle is being operated, a determination of the start time of vehicle operation is made and the start time is stored in memory 1004.

[0219] While the vehicle is operating, a determination of whether vehicle 1000 is still being operated is made repeatedly. If the vehicle ceases operation for at least a predetermined time, typically 5 minutes, a determination of the stop time of vehicle operation is made and the stop time is stored in memory 1004.

[0220] At any suitable time, whether the vehicle is operating or not operating, the contents of the memory 1004 may be downloaded to the central unit 1010.

[0221] Turning now to FIG. 9C, it is seen that a determination of whether vehicle 1100 is being operated is made repeatedly. If the vehicle is being operated, a determination of the start time of vehicle operation is made and the start time is stored in memory 1104.

[0222] While the vehicle is operating, a determination of whether vehicle 1100 is still being operated is made repeatedly. If the vehicle ceases operation for at least a predetermined time, typically 5 minutes, a determination of the stop time of vehicle operation is made and the stop time is stored in memory 1104.

[0223] At any suitable time, whether the vehicle is operating or not operating, the contents of the memory 1104 may be downloaded directly to central unit 1110. Alternatively, the contents of memory 1104 may be downloaded via the intermediate storage and communication unit 1108 to the central unit 1110 when the vehicle is at a suitable download location.

[0224] Reference is now made to FIGS. 10A, 10B & 10C, which are simplified pictorial illustrations of preferred embodiments of vehicle fee payment systems and methodologies constructed and operative in accordance with three alternative preferred embodiments of the present invention.

[0225] The embodiment of FIGS. 10A-10C may be employed for modulating traffic over given roads at given times or on given days. Thus, as appropriate, travel over certain routes may require payment of a fee, whereas travel over other alternative routes may require payment of a lesser fee or no fee at all.

[0226] It will be appreciated that the embodiment of FIGS. 10A-10C may also be employed for collecting user fees on toll roads. The embodiment of FIGS. 10A-10C may additionally be employed for collecting fees for entry into certain regions, such as areas of a city. Such fees may apply only at certain times or days and may vary from time to time or day to day.

[0227] Additionally in accordance with a preferred embodiment of the present invention, the embodiment of FIGS. 10A-10C may be employed for collecting fees that are duration-based solely or in combination with other time, date and/or location criteria. Thus, for example the fees payable may be a function not only of the time of day or date of entry, but also of the time duration that the vehicle is operating within a restricted area.

[0228]FIG. 10A shows a GPS based system wherein vehicles 1500 are each equipped with a GPS receiver 1502 which receives location inputs from satellites 1503. GPS receiver 1502 senses the location of each vehicle 1500 over time and provides an output indication of vehicle location as a function of time, which is preferably stored in a memory 1504 located in the vehicle 1500. The contents of the memory 1504 thus provide a record of whether the vehicle is being operated and where it has been traveling, without requiring or permitting driver intervention.

[0229] One or more of vehicles 1500 may also include vehicle operation monitors, such as a pollution monitor 1505. The output of the vehicle operation monitor, such as pollution monitor 1505 may also be stored in memory 1504.

[0230] As illustrated in FIG. 10A, an on-board communicator 1506 downloads data stored in memory 1504 and relating to vehicle operations over a time period extending from the preceding download, in a composite message, preferably in a wireless manner to a central unit 1510.

[0231] Typically, the composite message may be transmitted at any time from the communicator 1506 to the central unit 1510. The message typically includes data relating to the identity of the vehicle and the location of the vehicle during vehicle operation.

[0232] Composite messages may be transmitted at predetermined times or upon accumulation of data relating to a predetermined number of events or based on any other suitable criterion or combination of criteria.

[0233] Additionally or alternatively, communicator 1506 may communicate with the central unit 1510 via an intermediate storage and communication unit 1508, much in the same way as described hereinabove with reference to FIG. 7A.

[0234] It is appreciated that the functionality of FIG. 10A may also be applicable in vehicle insurance payment systems.

[0235]FIG. 10B shows a fixed infrastructure based system wherein vehicles 1600 are each equipped with a transmitter 1602, which transmits a wireless coded signal identifying the vehicle. Without requiring any intervention by the driver, the coded signal transmitted by transmitter 1602 is received by suitably located travel monitors 1604 which are preferably located in general propinquity to entrances to and exits from restricted or fee bearing locations. Such locations may be, for example, roads as shown in FIG. 10B or alternatively regions of a city where access is restricted or requires the payment of a fee.

[0236] The travel monitor 1604 senses the identity of each vehicle 1600 in suitable propinquity thereto and provides an output indication of the sensed vehicle presence at a given time, which is preferably stored in a memory 1606, preferably located at the travel monitor 1604. The combined contents of memories 1606 at suitably located travel monitors 1604 thus provide a record of where and when a vehicle has been or is traveling in a monitored travel space, without requiring or permitting driver intervention.

[0237] It may be appreciated that suitable location of travel monitors 1604 at the entrances and exits of roads may enable accurate and efficient collection of fees on roads and suitable location of travel monitors 1604 on access arteries to given regions may enable accurate and efficient collection of fees for access to such restricted or fee bearing areas.

[0238] As illustrated in FIG. 10B, a communicator 1608 associated with each travel monitor 1604 downloads data stored in memory 1606 and relating to vehicle operations over a time period extending from the preceding download, in a composite message, preferably in a wireless manner to a central unit 1610.

[0239] Typically, the composite message may be transmitted at any time from the communicator 1608 to the central unit 1610. The message typically includes data relating to the identity of the vehicle, the date and the time vehicle presence is sensed as well as the identity of the travel monitor 1604, which, of course, indicates its location.

[0240] Composite messages may be transmitted at predetermined times or upon accumulation of data relating to a predetermined number of events or based on any other suitable criterion or combination of criteria.

[0241] The central unit 1610 preferably employs the information contained in the composite messages received by it from various travel monitors 1604 to compute fees chargeable to individual vehicles, which are based, inter alia, on time duration of vehicle presence within given regions.

[0242]FIG. 10C shows a system wherein vehicles 1700 are each equipped with a receiver 1702 which receives coded location input signals from fixed local transmitters 1703. Receivers 1702 thus sense the presence of the vehicle 1700 at a given location at a given time.

[0243] The coded signals are transmitted by transmitters 1703 which are preferably located in general propinquity to entrances and exits from restricted or fee bearing locations. Such locations may be, for example, roads as shown in FIG. 10C or alternatively regions of a city where access is restricted or requires the payment of a fee.

[0244] The receiver 1702 senses the identity of each transmitter 1703 as the vehicle 1700 passes in suitable propinquity thereto and provides an output indication of the sensed vehicle presence at a given location at a given time, which is preferably stored in a memory 1706, located on-board the vehicle 1700. The contents of memory 1706 thus provide a record of where and when a vehicle has been or is traveling in a monitored travel space, without requiring or permitting driver intervention.

[0245] One or more of vehicles 1700 may also include vehicle operation monitors, such as a pollution monitor 1707. The output of the vehicle operation monitor, such as pollution monitor 1707 may also be stored in memory 1706. Vehicle operation monitors may be any suitable vehicle operation monitors, such as, for example, an on-board vehicle pollution monitor such as that described in U.S. Pat. No. 5,583,765, the disclosure of which is hereby incorporated by reference. It is appreciated that vehicle pollution over a given level may involve payment of a fee, which may be collected automatically by means of the system of FIGS. 10A & 10C.

[0246] As illustrated in FIG. 10C, an on-board communicator 1708 downloads data stored in memory 1706 and relating to vehicle operations over a time period extending from the preceding download, in a composite message, preferably in a wireless manner to a central unit 1710.

[0247] Typically, the composite message may be transmitted at any time from the communicator 1708 to the central unit 1710. The message typically includes data relating to the identity of the vehicle, the date and the time that the vehicle 1700 passes within predetermined propinquity of each of transmitters 1703.

[0248] Composite messages may be transmitted at predetermined times or upon accumulation of data relating to a predetermined number of events or based on any other suitable criterion or combination of criteria.

[0249] Additionally or alternatively, communicator 1706 may communicate with the central unit 1710 via an intermediate storage and communication unit 1712, much in the same way as described hereinabove with reference to FIG. 7A.

[0250] Reference is now made to FIGS. 11A, 11B and 11C which are simplified block diagram illustrations of preferred embodiments of vehicle fee payment systems and methodologies constructed and operative in accordance with a preferred embodiment of the present invention and corresponding to FIGS. 10A, 10B & 10C respectively.

[0251] Turning now to FIG. 11A, it is seen that vehicle 1500 includes a GPS receiver 1502 receiving inputs from satellites 1503. GPS receiver 1502 outputs to a CPU 1802 which interfaces with memory 1504 and with an optional display 1804. CPU also interfaces with on-board communicator 1506 and with a vehicle operation monitor, such as pollution monitor 1505.

[0252] As illustrated in FIG. 11A, when the vehicle 1500 is located at one of a multiplicity of predetermined download locations, such as a suitably equipped filling station, on-board communicator 1506 downloads data stored in memory 1504 and relating to vehicle operations over a time preferably extending since a previous download, typically in a wireless manner, to intermediate storage and communication unit 1508. The intermediate storage and communication unit 1508 includes a receiver or transceiver 1804 which interfaces with a CPU 1806. The CPU interfaces with a memory 1808 which stores data relating to vehicle operations in respect of a multiplicity of vehicles and with a communicator 1810, which communicates this data, in a composite message, preferably in a wireless manner, to central unit 1510.

[0253] Central unit 1510 preferably includes a receiver or transceiver 1812 which interfaces with a CPU 1814. The CPU 1814 in turn interfaces with a database 1816. The database accumulates the content of the composite messages received by the central unit 1510 and supplies this content in an appropriate form to a billing system 1818.

[0254] Additionally or alternatively, communicator 1506 may communicate directly with the central unit 1510, bypassing the intermediate storage and communication unit 1508. In such a case, units 1508 may be obviated.

[0255]FIG. 11B shows that vehicle 1600 includes transmitter 1602, which transmits a wireless coded signal identifying the vehicle, without requiring any intervention by the driver.

[0256] The coded signal transmitted by transmitter 1602 is received by travel monitors 1604 which are located in general propinquity to entrances and exits from restricted or fee bearing locations. Such locations may be, for example, roads as shown in FIG. 10B or alternatively regions of a city where access is restricted or requires the payment of a fee.

[0257] Each travel monitor 1604 preferably includes a receiver 1900 which interfaces with a CPU 1902. CPU 1902 interfaces with memory 1606 and with communicator 1608.

[0258] As illustrated in FIG. 11B, communicator 1608 associated with each travel monitor 1604 downloads data stored in memory 1606 and relating to vehicle operations over a time period extending from the preceding download, in a composite message, preferably in a wireless manner, to central unit 1610.

[0259] Typically, the composite message may be transmitted at any time from the communicator 1608 to the central unit 1610. The message typically includes data relating to the identity of the vehicle, the date and the time vehicle presence is sensed as well as the identity of the travel monitor 1604, which, of course, indicates its location.

[0260] Composite messages may be transmitted at predetermined times or upon accumulation of data relating to a predetermined number of events or based on any other suitable criterion or combination of criteria.

[0261] The central unit 1610 preferably employs the information contained in the composite messages received by it from various travel monitors 1604 to compute fees chargeable to individual vehicles, which are based, inter alia, on time duration of vehicle presence within given regions.

[0262] Central unit 1610 typically includes a communicator 1908 which interfaces with a CPU 1910. CPU 1910 preferably interfaces with a database 1912 and outputs to a billing system 1914. Communication between communicators 1608 and 1908 may be wired or wireless.

[0263] Turning now to FIG. 11C, it is seen that vehicle 1700 includes a receiver 1702 receiving inputs from transmitters 1703. Receiver 1702 outputs to a CPU 2002 which interfaces with memory 1706 and with an optional display 2004. CPU 2002 also interfaces with on-board communicator 1708 and with a vehicle operation monitor, such as pollution monitor 1707.

[0264] As illustrated in FIG. 10C, when the vehicle 1700 is located at one of a multiplicity of predetermined download locations, such as a suitably equipped filling station, on-board communicator 1708 downloads data stored in memory 1706 relating to vehicle operations over a time preferably extending since a previous download, typically in a wireless manner, to intermediate storage and communication unit 1712. The intermediate storage and communication unit 1712 includes a receiver or transceiver 2006 which interfaces with a CPU 2008. The CPU 2008 interfaces with a memory 2010 which stores data relating to vehicle operations in respect of a multiplicity of vehicles and with a communicator 2012, which communicates this data, in a composite message, preferably in a wireless manner to central unit 1710.

[0265] Central unit 1710 preferably includes a receiver or transceiver 2014 which interfaces with a CPU 2016. The CPU 2016 in turn interfaces with a database 2018. The database accumulates the content of the composite messages received by the central unit 1710 and supplies this content in an appropriate form to a billing system 2020.

[0266] Additionally or alternatively, communicator 1708 may communicate directly with the central unit 1710, by passing the intermediate storage and communication unit 1712. In such a case, units 1712 may be obviated.

[0267] Reference is now made to FIGS. 12A, 12B & 12C which are simplified flow charts illustrating the operation of preferred embodiments of vehicle fee payment systems and methodologies of FIGS. 10A & 11A, 10B & 11B and 10C & 11C.

[0268] Turning now to FIG. 12A, it is seen that a determination of the location of vehicle 1500 is made repeatedly and the location of the vehicle 1500 as a function of time is stored in memory 1504 for such times as the vehicle 1500 is being operated. Preferably, an output from a vehicle operation monitor such as pollution monitor 1505 is also stored in the memory.

[0269] At any suitable time when the vehicle is located at a suitable download location, whether the vehicle is operating or not operating, the contents of the memory 1504 may be downloaded to the intermediate storage and communication unit 1508 and thence to the central unit 1510. Alternatively or additionally, the contents of memory 1504 may be downloaded directly to the central unit 1510.

[0270] Turning now to FIG. 12B, it is seen that the travel monitors 1604 continuously record the identity of vehicles in predetermined propinquity thereto as well as the time of such propinquity. This information is stored in memories 1606 of monitors 1604.

[0271] At any suitable time, the contents of the memories 1606 may be downloaded to the central unit 1610, which processes them into vehicle specific information useful for billing functionality and supplies the contents of memory 1604 to billing system 1914.

[0272] Turning now to FIG. 12C, it is seen that receiver 1702 records instances when vehicle 1700 is in predetermined propinquity to a transmitter 1703 as well as the time of such propinquity. This information is stored in memory 1706.

[0273] At any suitable time, the contents of the memories 1706 of vehicles 1700 may be downloaded to the intermediate storage and communication unit 1712 and thence to the central unit 1710. Alternatively or additionally, the contents of memory 1706 may be downloaded directly to the central unit 1710.

[0274] Reference is now made to FIGS. 13A, 13B and 13C, which are simplified pictorial illustrations of three alternative embodiments of vehicle-related services payment systems and methodologies constructed and operative in accordance with another preferred embodiment of the present invention and which preferably are characterized in that the payment in respect of a vehicle-related service is dependent on at least one of the mileage traveled by a vehicle and the time of day that the vehicle is being operated and preferably is dependent on both.

[0275] Important examples of such systems and methodologies include vehicle insurance billing and vehicle fee payment systems wherein the only variables, sensed by an on-board vehicle sensor, which are considered in the billing data are vehicle mileage and time of day or night of vehicle use. Other types of such systems and methodologies are also within the scope of the present invention.

[0276] Turning now to FIG. 13A, there is seen a vehicle 2100 equipped with a vehicle movement or other vehicle operation determining sensor 2102. Sensor 2102 is typically a mileage sensor of any suitable design or principle of operation. Sensor 2102 need not necessarily be connected to the electrical system of the vehicle 2100.

[0277] Without requiring any intervention by the driver, the times when a driver moves the vehicle 2100 and subsequently parks the vehicle 2100 as well as the accrued mileage are recorded in a memory 2104, which may store a series of vehicle operation start and stop records as well as mileage records.

[0278] As illustrated in FIG. 13A, when the vehicle 2100 is located at one of a multiplicity of predetermined download locations, such as a suitably equipped filling station, an on-board communicator 2106 downloads data stored in memory 2104 and relating to a plurality of vehicle operation start and stop events as well as mileage records, typically in a wireless manner, to an intermediate storage and communication unit 2108, typically located at the filling station. The intermediate storage and communication unit 2108 preferably receives and stores data relating to a plurality of vehicle operation start and stop events as well as mileage records in respect of a multiplicity of vehicles and communicates this data, in a composite message, preferably in a wireless manner to a central unit 2110. Alternatively or additionally, download locations may be found at other locations, such as road intersections, parking lots and malls.

[0279] Typically, the composite message may be transmitted at any time from the intermediate storage and communication unit 2108 to the central unit 2110. Such a composite message typically includes messages relating to a plurality of vehicle operation start and stop events and corresponding mileage records for a multiplicity of different vehicles. In respect of each such event, the message typically includes data relating to the identity of the vehicle, the date, the start time of vehicle operation, the stop time of vehicle operation and the mileage.

[0280] Composite messages may be transmitted at predetermined times or upon accumulation of data relating to a predetermined number of events or based on any other suitable criterion or combination of criteria.

[0281] Turning now to FIG. 13B, there is seen a vehicle 2200 equipped with a movement or operation determining sensor 2202. Sensor 2202 is typically a mileage sensor of any suitable design or principle of operation. Sensor 2202 need not necessarily be connected to the electrical system of the vehicle 2200.

[0282] Without requiring any intervention by the driver, the times when a driver moves the vehicle 2200 and subsequently parks the vehicle 2200 as well as the accrued mileage are recorded in a memory 2204, which may store a series of vehicle operation start and stop records as well as mileage records.

[0283] As illustrated in FIG. 13B, an on-board communicator 2206 downloads data stored in memory 2204 and relating to a plurality of vehicle operation start and stop events and corresponding mileage records, in a composite message, preferably in a wireless manner to a central unit 2210.

[0284] Typically, the composite message may be transmitted at any time from the communicator 2206 to the central unit 2210. Such a composite message typically includes messages relating to a plurality of vehicle operation start and stop events and corresponding mileage records. In respect of each such event, the message typically includes data relating to the identity of the vehicle, the date, the start time of vehicle operation and the stop time of vehicle operation as well as mileage records.

[0285] Composite messages may be transmitted at predetermined times or upon accumulation of data relating to a predetermined number of events or based on any other suitable criterion or combination of criteria.

[0286] Turning now to FIG. 13C, there is seen a vehicle 2300 equipped with a GPS receiver 2302 receiving inputs from satellites 2303 or similar location determining device. The GPS receiver 2302 senses when the location of the vehicle changes.

[0287] Without requiring any intervention by the driver, the times when a driver moves the vehicle 2300 and subsequently parks the vehicle 2300 as well as the corresponding accrued mileage are recorded in a memory 2304, which may store a series of vehicle operation start and stop records as well as mileage records.

[0288] As illustrated in FIG. 13C, an on-board communicator 2306 downloads data stored in memory 2304 and relating to a plurality of vehicle operation start and stop events and accrued mileage, in a composite message, preferably in a wireless manner to a central unit 2310.

[0289] Typically, the composite message may be transmitted at any time from the communicator 2306 to the central unit 2310. Such a composite message typically includes messages relating to a plurality of vehicle operation start and stop events and accrued mileage. In respect of each such event, the message typically includes data relating to the identity of the vehicle, the date, the start time of vehicle operation and the stop time of vehicle operation as well as the accrued mileage.

[0290] Composite messages may be transmitted at predetermined times or upon accumulation of data relating to a predetermined number of events or based on any other suitable criterion or combination of criteria.

[0291] Additionally or alternatively, communicator 2306 may communicate with the central unit 2310 via an intermediate storage and communication unit 2308, much in the same way as described hereinabove with reference to FIG. 13A.

[0292] Reference is now made to FIGS. 14A, 14B and 14C, which are simplified block diagram illustrations of three alternative embodiments of vehicle-related services payment systems and methodologies constructed and operative in accordance with a preferred embodiment of the present invention and corresponding to FIGS. 13A, 13B & 13C respectively.

[0293] Turning now to FIG. 14A, it is seen that vehicle 2100 includes a CPU 2402, which interfaces with sensor 2102, memory 2104 and on-board communicator 2106.

[0294] As illustrated in FIG. 14A, when the vehicle 2100 is located at one of a multiplicity of predetermined download locations, such as a suitably equipped filling station, on-board communicator 2106 downloads data stored in memory 2104 and relating to a plurality of vehicle operation start and stop events and corresponding mileage records, typically in a wireless manner, to intermediate storage and communication unit 2108. The intermediate storage and communication unit 2108 includes a receiver or transceiver 2404 which interfaces with a CPU 2406. The CPU interfaces with a memory 2408 which stores data relating to a plurality of vehicle operation start and stop events and corresponding accrued mileage in respect of a multiplicity of vehicles and with a communicator 2410, which communicates this data, in a composite message, preferably in a wireless manner, to central unit 2110.

[0295] Central unit 2110 preferably includes a receiver or transceiver 2412 which interfaces with a CPU 2414. The CPU 2414 in turn interfaces with a database 2416. The database accumulates the content of the composite messages received by the central unit 2110 and supplies this content in an appropriate form to a billing system 2418. The billing system 2418 may take into account appropriate additional criteria, such as, for example in the case of insurance, the age and driving experience of a driver and various characteristics of the vehicle or in the case of vehicle-related fees, the type and weight of the vehicle.

[0296] Turning now to FIG. 14B, it is seen that vehicle 2200 includes a CPU 2502, which interfaces with sensor 2202, memory 2204 and on-board communicator 2206.

[0297] As illustrated in FIG. 14B, on-board communicator 2206 downloads data stored in memory 2204 and relating to one or more vehicle operation start and stop events and accrued mileage records, typically in a wireless manner, to central unit 2210. Central unit 2210 preferably includes a receiver or transceiver 2512 which interfaces with a CPU 2514. The CPU 2514 in turn interfaces with a database 2516. The database accumulates the content of the composite messages received by the central unit 2210 and supplies this content in an appropriate form to a billing system 2518.

[0298] Turning now to FIG. 14C, it is seen that vehicle 2300 includes a GPS receiver 2302 receiving inputs from satellites 2303. GPS receiver 2302 outputs to a CPU 2602 which interfaces with memory 2304 and with an optional display 2604. CPU 2602 also interfaces with on-board communicator 2306.

[0299] As illustrated in FIG. 14C, when the vehicle 2300 is located at one of a multiplicity of predetermined download locations, such as a suitably equipped filling station, on-board communicator 2306 downloads data stored in memory 2304 and relating to a plurality of vehicle operation start and stop events as well as accrued mileage, typically in a wireless manner, to intermediate storage and communication unit 2308. The intermediate storage and communication unit 2308 includes a receiver or transceiver 2605 which interfaces with a CPU 2606. The CPU interfaces with a memory 2608 which stores data relating to a plurality of vehicle operation start and stop events as well as accrued mileage in respect of a multiplicity of vehicles and with a communicator 2610, which communicates this data, in a composite message, preferably in a wireless manner to central unit 2310.

[0300] Central unit 2310 preferably includes a receiver or transceiver 2612 which interfaces with a CPU 2614. The CPU 2614 in turn interfaces with a database 2616. The database accumulates the content of the composite messages received by the central unit 2310 and supplies this content in an appropriate form to a billing system 2618.

[0301] Additionally or alternatively, communicator 2306 may communicate directly with the central unit 2310, bypassing the intermediate storage and communication unit 2308. In such a case, units 2308 may be obviated.

[0302] Reference is now made to FIGS. 15A, 15B and 15C, which are simplified flow charts illustrating the operation of the three alternative embodiments of payment systems and methodologies of FIGS. 13A & 14A, 13B & 14B and 13C & 14C, respectively.

[0303] Turning now to FIG. 15A, it is seen that a determination of whether vehicle 2100 is being operated is made repeatedly. If the vehicle is being operated, a determination of the start time of vehicle operation is made, a mileage count is started and the start time is stored in memory 2104.

[0304] While the vehicle is operating, a determination of whether vehicle 2100 is still being operated is made repeatedly. If the vehicle ceases operation for at least a predetermined time, typically 5 minutes, a determination of the stop time of vehicle operation is made and the stop time and accrued mileage are stored in memory 2104.

[0305] At any suitable time when the vehicle is located at a suitable download location, whether the vehicle is operating or not operating, the contents of the memory 2104 may be downloaded to the intermediate storage and communication unit 2108 and thence to the central unit 2110.

[0306] Turning now to FIG. 15B, it is seen that a determination of whether vehicle 2200 is being operated is made repeatedly. If the vehicle is being operated, a mileage count is started, a determination of the start time of vehicle operation is made and the start time is stored in memory 2204.

[0307] While the vehicle is operating, a determination of whether vehicle 2200 is still being operated is made repeatedly. If the vehicle ceases operation for at least a predetermined time, typically 5 minutes, a determination of the stop time of vehicle operation is made and the stop time and accrued mileage are stored in memory 2204.

[0308] At any suitable time, whether the vehicle is operating or not operating, the contents of the memory 2204 may be downloaded to the central unit 2210.

[0309] Turning now to FIG. 15C, it is seen that a determination of whether vehicle 2300 is being operated is made repeatedly. If the vehicle is being operated, a mileage count is started, a determination of the start time of vehicle operation is made and the start time is stored in memory 2304.

[0310] While the vehicle is operating, a determination of whether vehicle 2300 is still being operated is made repeatedly. If the vehicle ceases operation for at least a predetermined time, typically 5 minutes, a determination of the stop time of vehicle operation is made and the stop time and accrued mileage are stored in memory 2304.

[0311] At any suitable time, whether the vehicle is operating or not operating, the contents of the memory 2304 may be downloaded directly to central unit 2310. Alternatively, the contents of memory 2304 may be downloaded via the intermediate storage and communication unit 2308 to the central unit 2310 when the vehicle is at a suitable download location.

[0312] It will be appreciated by persons skilled in the art that the present invention is not limited by what has been particularly shown and described hereinabove. Rather the scope of the present invention includes both combinations and subcombinations of the various features described hereinabove as well as variations and modifications which would occur to persons skilled in the art upon reading the specification and which are not in the prior art. 

1. A vehicle-related services system comprising: at least one sensor automatically sensing at least one of the time during which a vehicle is not being operated and where said vehicle is located when it is not being operated; and at least one data processor receiving information sensed by said at least one sensor, indicating at least one of the time during which said vehicle is not being operated and where said vehicle is located when it is not being operated and providing a billing data output in respect of a vehicle-related service which is dependent on at least one of the time during which said vehicle is not being operated and where said vehicle is located when it is not being operated.
 2. A vehicle-related services system according to claim 1 and wherein said at least one sensor automatically senses the time of day and date when said vehicle is not being operated.
 3. A vehicle-related services system according to claim 1 and wherein said at least one sensor automatically senses the time duration during which said vehicle is not being operated.
 4. A vehicle-related services system according to claim 2 and wherein said at least one sensor automatically senses the time duration during which said vehicle is not being operated.
 5. A vehicle-related services system according to claim 1 and wherein: said at least one sensor automatically senses the time during which a vehicle is not being operated and where said vehicle is located when it is not being operated; and said at least one data processor receives information sensed by said at least one sensor, indicating the time during which said vehicle is not being operated and where said vehicle is located when it is not being operated and provides a billing data output in respect of a vehicle-related service which is dependent on the time during which said vehicle is not being operated and where said vehicle is located when it is not being operated.
 6. A vehicle-related services system according to claim 5 and wherein: said at least one sensor automatically senses the time during which a vehicle is parked and where said vehicle is located when it is parked; and said at least one data processor receives information sensed by said at least one sensor, indicating the time during which said vehicle is parked and where said vehicle is parked and provides a parking data output in respect of parking, which is dependent on the time during which said vehicle is parked and where said vehicle is parked.
 7. A vehicle-related services system according to claim 6 and wherein said at least one sensor and said at least one data processor are operative without vehicle operator initiative to provide an indication of at least one of the time during which said vehicle is parked and where said vehicle is parked.
 8. A vehicle-related services system according to claim 6 and wherein said sensor is on-board said vehicle.
 9. A vehicle-related services system according to claim 6 and also comprising: at least one communicator on-board said vehicle providing an output indicating the time during which vehicle is parked and where said vehicle is parked; and a receiver associated with said at least one data processor for receiving a communication from said at least one communicator and employing said communication for providing said information to said at least one data processor.
 10. A vehicle-related services system according to claim 9 and wherein said communicator communicates with said receiver at least partially not in real time.
 11. A vehicle-related services system according to claim 9 and wherein said communicator communicates with an intermediate storage and communication unit only when a vehicle in which said communicator is located is at one of a plurality of predetermined locations.
 12. A vehicle-related services system according to claim 11 and wherein said intermediate storage and communication unit is located at a vehicle fueling station.
 13. A vehicle-related services system according to claim 6 and wherein said information includes identification of a street parking location in which said vehicle is stationary for at least a predetermined amount of time.
 14. A vehicle-related services system according to claim 8 and wherein said at least one sensor is operative to sense the time during which a vehicle is not being operated without requiring interaction with an indicating device fixed in propinquity to said location.
 15. A vehicle-related services system according to claim 6 and wherein said at least one sensor is operative using triangulation to determine where a vehicle is parked.
 16. A vehicle-related services system according to claim 9 and also comprising at least one on-board vehicle potential additional parking space sensor which is operative when a vehicle is stationary at a street parking place for indicating whether at least one potential additional adjacent parking place is unoccupied.
 17. A vehicle-related services system according to claim 16 wherein said at least one on-board vehicle communicator provides an output indicating existence of at least one potential unoccupied additional adjacent parking place, the system also comprising: a street parking map database indicating legal street parking spaces; a correlator receiving said output indicating existence of at least one potential unoccupied additional adjacent parking place and correlating it with said legal street parking spaces; and an available parking communicator providing information regarding unoccupied legal street parking places to at least one driver.
 18. A vehicle-related services system including: a plurality of on-board potential additional parking space sensors located on a plurality of vehicles, which sensors each provide an output indicating existence of at least one potential unoccupied additional adjacent parking place adjacent a vehicle located in a street parking location; and an available parking communicator employing information received from said plurality of sensors and providing information regarding unoccupied street parking places to at least one driver.
 19. A vehicle-related services system according to claim 18 and also comprising: a street parking map database indicating legal street parking spaces; and a correlator receiving said output indicating existence of at least one potential unoccupied additional adjacent parking place and correlating it with said legal street parking spaces.
 20. A vehicle-related services system according to claim 1 and wherein said at least one data processor comprises a vehicle insurance billing data processor.
 21. A vehicle-related services system according to claim 20 and wherein said billing data comprises vehicle insurance billing data wherein the only variables, sensed by said on-board vehicle sensor, which are considered in said billing data are duration of vehicle operation and time of day or night of vehicle operation.
 22. A vehicle-related services system according to claim 1 and wherein said billing data comprises vehicle insurance billing data wherein the said billing data is not dependent on vehicle speed.
 23. A vehicle-related services system comprising: at least one sensor on-board a vehicle and automatically sensing at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated; at least one communicator on-board said vehicle providing an output indicating at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated; and at least one data processor receiving a communication from said at least one communicator, indicating at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated and providing a billing data output in respect of a vehicle-related service which is dependent only on at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated.
 24. A vehicle-related services system comprising: at least one sensor on-board a vehicle and automatically sensing only at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated; at least one communicator on-board said vehicle providing an output indicating at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated; and at least one data processor receiving a communication from said at least one communicator, indicating at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated and providing a billing data output in respect of a vehicle-related service which is dependent on at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated.
 25. A vehicle-related services system according to claim 23 and wherein said at least one data processor comprises a vehicle insurance billing data processor.
 26. A vehicle-related services system according to claim 25 and wherein said communicator communicates with an intermediate storage and communication unit only when a vehicle in which said communicator is located is at one of a plurality of predetermined locations.
 27. A vehicle-related services system according to claim 26 and wherein said intermediate storage and communication unit is located at a vehicle fueling station.
 28. A vehicle-related services system according to claim 24 and wherein said at least one data processor comprises a vehicle insurance billing data processor.
 29. A vehicle-related services system according to claim 25 and wherein said billing data comprises vehicle insurance billing data wherein the only variables, sensed by said on-board vehicle sensor, which are considered in said billing data are duration of vehicle operation and time of day or night of vehicle operation.
 30. A vehicle-related services system according to claim 25 and wherein said billing data comprises vehicle insurance billing data wherein the only variables, sensed by said on-board vehicle sensor, which are considered in said billing data are duration of vehicle operation and location of the vehicle during said vehicle operation.
 31. A vehicle-related services system according to claim 28 and wherein said billing data comprises vehicle insurance billing data wherein the only variables, sensed by said on-board vehicle sensor, which are considered in said billing data are duration of vehicle use and time of day or night of vehicle use.
 32. A vehicle-related services system comprising: at least one sensor on-board a vehicle and automatically sensing at least one of the time during which said vehicle is being operated and the distance traveled by said vehicle while it is being operated; at least one communicator on-board said vehicle providing an output indicating at least one of the time during which said vehicle is being operated and the distance traveled by said vehicle while it is being operated; and at least one data processor receiving a communication from said at least one communicator, indicating at least one of the time during which said vehicle is being operated and the distance traveled by said vehicle while it is being operated; and providing a billing data output in respect of a vehicle-related service which is dependent only on at least one of the time during which said vehicle is being operated and the distance traveled by said vehicle while it is being operated.
 33. A vehicle-related services system according to claim 32 and wherein said at least one data processor comprises a vehicle insurance billing data processor.
 34. A vehicle-related services system according to claim 33 and wherein said billing data comprises vehicle insurance billing data wherein the only variables, sensed by said on-board vehicle sensor, which are considered in said billing data are time of day and date of vehicle operation and distance covered during said vehicle operation.
 35. A vehicle-related services system according to claim 33 and wherein said communicator communicates with an intermediate storage and communication unit only when a vehicle in which said communicator is located is at one of a plurality of predetermined locations.
 36. A vehicle-related services system according to claim 35 and wherein said intermediate storage and communication unit is located at a vehicle fueling station.
 37. A vehicle-related services system according to claim 25 and wherein said billing data comprises vehicle insurance billing data wherein the said billing data is not dependent on vehicle speed.
 38. A vehicle-related services system according to claim 23 and wherein said at least one data processor comprises a vehicle parking billing data processor.
 39. A vehicle-related services system according to claim 38 and wherein said at least one sensor and said at least one data processor are operative without vehicle operator initiative to provide an indication of at least one of the time during which said vehicle is parked and where said vehicle is parked.
 40. A vehicle-related services system according to claim 38 and wherein said at least one sensor is operative to sense the time during which a vehicle is being operated without requiring interaction with an indicating device fixed in propinquity to said location.
 41. A vehicle-related services system according to claim 38 and wherein said communicator communicates with said at least one data processor at least partially not in real time.
 42. A vehicle-related fee payment system comprising: at least one sensor on-board a vehicle and automatically sensing at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated; at least one communicator on-board said vehicle providing an output indicating at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated; and at least one data processor receiving a communication from said at least one communicator, indicating at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated and providing a billing data output in respect of a vehicle-related use fee which is dependent on the time during which said vehicle is being operated.
 43. A vehicle-related fee payment system according to claim 42 and wherein said communicator communicates with said at least one data processor at least partially not in real time.
 44. A vehicle-related fee payment system according to claim 42 and wherein said communicator communicates with an intermediate storage and communication unit only when a vehicle in which said communicator is located is at one of a plurality of predetermined locations.
 45. A vehicle-related fee payment system according to claim 44 and wherein said intermediate storage and communication unit is located at a vehicle fueling station.
 46. A vehicle-related fee payment system according to claim 42 and wherein said at least one data processor provides a billing data output in respect of a vehicle-related use fee which is dependent on the duration of vehicle operation and time of day of vehicle operation.
 47. A vehicle-related fee payment system according to claim 46 and wherein said at least one data processor provides a billing data output in respect of a vehicle-related use fee which is also dependent on where said vehicle is located during vehicle operation.
 48. A vehicle-related fee payment system according to claim 42 and wherein said billing data output is dependent on the time during which said vehicle is being operated and on a level of pollution being created by said vehicle.
 49. A vehicle-related fee payment system comprising: at least one sensor for automatically sensing the passage of a vehicle along a given road; at least one data processor receiving a communication from said at least one sensor, indicating the passage of said vehicle along a given road at a given time and providing a billing data output in respect of a vehicle-related use fee which is dependent only on the time during which said vehicle is passing along said given road.
 50. A vehicle-related fee payment system comprising: at least one sensor on-board a vehicle and automatically sensing at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated; at least one communicator on-board said vehicle providing an output indicating at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated; and at least one data processor receiving a communication from said at least one communicator, indicating at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated and providing a billing data output in respect of a vehicle-related use fee which is dependent on the region in which a vehicle is operating and the time of day during which said vehicle is being operated in said region.
 51. A vehicle-related services method comprising: automatically sensing the time during which a vehicle is not being operated and where said vehicle is located when it is not being operated; and receiving information indicating the time during which said vehicle is not being operated and where said vehicle is located when it is not being operated and providing a parking data output in respect of a vehicle-related service which is dependent on the time during which said vehicle is not being operated and where said vehicle is located when it is not being operated.
 52. A vehicle-related services method according to claim 51 and providing an indication of the time during which said vehicle is parked and where said vehicle is parked substantially without operator intervention.
 53. A vehicle-related services method according to claim 51 and also comprising communicating an indication of the time during which said vehicle is parked and where said vehicle is parked to a receiver at least partially not in real time.
 54. A vehicle-related services method according to claim 51 and wherein said automatic sensing takes place without requiring interaction with an indicating device fixed in propinquity to a parking location.
 55. A vehicle-related services method including: providing outputs indicating existence of at least one potential unoccupied additional adjacent parking place adjacent a plurality of vehicles located in street parking locations; and employing said outputs received from said plurality of vehicles and providing information regarding unoccupied street parking places to at least one driver.
 56. A vehicle-related services method comprising: automatically sensing at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated; communicating an output indicating at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated; and receiving a communication indicating at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated and providing an insurance billing data output in respect of vehicle insurance which is dependent only on at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated.
 57. A vehicle-related services method according to claim 56 and wherein said communicating takes place only when a vehicle is at one of a plurality of predetermined locations.
 58. A vehicle-related services method according to claim 56 and wherein said billing data comprises vehicle insurance billing data wherein the only automatically sensed variables which are considered in said billing data are duration of vehicle operation and time of day or night of vehicle operation.
 59. A vehicle-related fee payment method comprising: automatically sensing at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated; providing an output indicating at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated; and receiving said output indicating at least one of the time during which said vehicle is being operated and where said vehicle is located when it is being operated and providing a billing data output in respect of a vehicle-related use fee which is dependent on the time during which said vehicle is being operated.
 60. A vehicle-related fee payment method according to claim 59 and wherein said billing data output in respect of a vehicle-related use fee is dependent on the duration of vehicle operation and time of day of vehicle operation.
 61. A vehicle-related fee payment method according to claim 59 and wherein said billing data output is dependent on the time during which said vehicle is being operated and on a level of pollution being created by said vehicle.
 62. A vehicle-related services method comprising: automatically sensing the time during which said vehicle is being operated and the distance traveled by said vehicle while it is being operated; communicating an output indicating the time during which said vehicle is being operated and the distance traveled by said vehicle while it is being operated; and receiving a communication indicating the time during which said vehicle is being operated and the distance traveled by said vehicle while it is being operated and providing an insurance billing data output in respect of vehicle insurance which is dependent only on the time during which said vehicle is being operated and the distance traveled by said vehicle while it is being operated.
 63. A vehicle-related services method according to claim 62 and wherein said billing data comprises vehicle insurance billing data wherein the only automatically sensed variables which are considered in said billing data are the distance traveled by said vehicle while it is being operated and time of day or night of vehicle operation. 